Zadig 文档
Zadig
教程
博客
论坛
关于
中文英文
Zadig
教程
博客
论坛
关于
Zadig v4.1
Loading...
     编辑文档
     反馈问题
     社区讨论

    本页导航

    Using Helm

    This guide describes how to install Zadig using Helm, suitable for production environments.

    # Resource Preparation

    1. Kubernetes cluster, version v1.16+, recommended 8C16G, admin privileges

      Zadig itself consumes 4C8G and supports two concurrent workflow tasks

    2. Helm tool, version v3.5+ (download here(opens new window))
    3. Network:
      • For IP+Port access, ensure cluster nodes have external IPs
      • For domain access, prepare a valid domain and direct traffic to the gateway-proxy service

    Tip

    1. If you use built-in storage components (MySQL/MongoDB/MinIO), configure the default StorageClass in Kubernetes for PVC persistence before installation
    2. Some cluster network plugins may prevent Service backend Pods from self-access; please verify in advance
    3. Configure kube-dns to ensure name-based addressing between services and Pods

    # Installation

    Use the official installation assistant(opens new window) for one-click installation. For detailed parameters, see Chart Parameter List.

    Installation time depends on hardware and network. Use kubectl -n {Namespace} get pod to check service status; all RUNNING means success.

    Tip

    See License for license setup.

    # Upgrade

    To upgrade Zadig, follow these steps:

    # Step 1: Confirm Version

    • Confirm the current and target Zadig versions. Do not skip versions; upgrade step by step.

    Use helm list -n {Namespace} to check the current version.

    # Step 2: Backup Data and Parameters

    • See Backup Data
    • Backup parameters: helm get values -n {Namespace} {ReleaseName} > zadig.yaml

    # Step 3: Perform the Upgrade

    • Do not use Zadig during the upgrade
    • Upgrade command:
      helm repo add koderover-chart https://koderover.tencentcloudcr.com/chartrepo/chart
      helm repo update
      helm upgrade {releaseName} -n {Namespace} --version=4.1.0 koderover-chart/zadig -f zadig.yaml
      
      1
      2
      3

    # Step 4: Upgrade Check

    Check the following to verify the upgrade:

    1. Account login works
    2. Project/environment/service/integration data is normal
    3. Environment and service data display correctly
    4. Product/custom workflows (if any) run normally

    # Uninstall

    • Uninstalling Zadig does not delete environments, services, etc. created by Zadig; clean up manually if needed
    • Uninstall command:
      helm uninstall {ReleaseName} -n {Namespace}
      
      1

    # Zadig Chart Parameter List

    Zadig Chart includes MySQL, MongoDB, and MinIO. You can choose whether to install these components as needed.

    # Gateway Proxy Parameters

    KeyDescriptionValue ExampleDefault Value
    gloo.gatewayProxies.gatewayProxy.service.typeThe exposure method of the Gateway Proxy service, options include LoadBalancer, NodePort, and ClusterIPLoadBalancerLoadBalancer

    # MongoDB Parameters

    • Connection parameters
    KeyDescriptionValue ExampleDefault Value
    connections.mongodb.connectionStringMongoDB connection stringmongodb://root:zadig@kr-mongodb:27017mongodb://root:zadig@kr-mongodb:27017
    connections.mongodb.dbThe DB used by Zadig for MongoDBzadigzadig
    ee.mongodb.enableTransactionWhether to enable transaction functionality. The actual effectiveness of transactions depends on the MongoDB version and installation method. Refer to the official MongoDB documentation for more informationfalsefalse
    ee.mongodb.dbThe DB used by Zadig for delivery and deployment components, which must not be the same as the value of connections.mongodb.dbplutus_zadigplutus_zadig
    • Built-in MongoDB Installation Parameters
    KeyDescriptionValue ExampleDefault Value
    tags.mongodbWhether to install the built-in MongoDBtruetrue
    mongodb.persistence.enabledMongoDB persistence switchtruetrue
    mongodb.persistence.sizeMongoDB storage space size20 Gi20 Gi
    mongodb.rootPasswordBuilt-in MongoDB root user passwordzadignil
    mongodb.persistence.existingClaimIf the installed MongoDB needs to use an existing PVC, use this field to specify the Claim Namemyclaimnil
    • External MongoDB (version 4.4+)
    KeyDescriptionValue ExampleDefault Value
    tags.mongodbWhether to install the built-in MongoDBfalsetrue
    connections.mongodb.connectionStringThe connection string for the Zadig system's business database, escape special characters if multiple addresses are configuredmongodb://user:password
    @8.10.20.20\,8.10.20.30
    mongodb://zadig-mongodb:27017
    connections.mongodb.dbThe default DB used by the Zadig systemzadigzadig
    ee.mongodb.dbThe DB used by Zadig for delivery and deployment components, which must not be the same as the value of connections.mongodb.dbplutus_zadigplutus_zadig

    # MinIO Parameters

    Tip

    If you have your own S3 object storage, you can skip MinIO. See Object Storage.

    • Built-in MinIO Installation Parameters
    KeyDescriptionValue ExampleDefault Value
    tags.minioWhether to install the built-in MinIOtruetrue
    minio.persistence.enabledMinIO object storage persistence switchtruetrue
    minio.persistence.sizeMinIO storage space size20 Gi20 Gi
    minio.persistence.storageClassThe Storage Class used by MinIO's PVC. If persistence is enabled and no Storage Class or existingClaim is provided, the default Storage Class of the cluster will be used. If the cluster does not have a default Storage Class, the installation will fail.storage_classnil
    minio.persistence.existingClaimIf the installed MinIO needs to use an existing PVC, use this field to specify the Claim Namemy_pvcnil

    # MySQL Parameters

    • Connection parameters
    KeyDescriptionValue ExampleDefault Value
    connections.mysql.hostMySQL connection informationkr-mysql:3306kr-mysql:3306
    connections.mysql.auth.userMySQL usernamerootroot
    connections.mysql.auth.passwordMySQL passwordzadigzadig
    connections.mysql.db.userThe DB used by the Zadig user systemuseruser
    connections.mysql.db.dexThe DB used by the Zadig third-party connector Dexdexdex
    dex.config.storage.config.databaseThe DB used by the Dex system, which must be the same as the value of connections.mysql.db.dexdexdex
    dex.config.storage.config.hostThe MySQL Host used by the Dex systemzadig-mysqlzadig-mysql
    dex.config.storage.config.portThe MySQL port used by the Dex system33063306
    dex.config.storage.config.userThe MySQL username used by the Dex systemrootroot
    dex.config.storage.config.passwordThe MySQL password used by the Dex systemzadigzadig
    • Built-in MySQL Installation Parameters
    KeyDescriptionValue ExampleDefault Value
    tags.mysqlWhether to install the built-in MySQLtruetrue
    mysql.rootPasswordMySQL passwordzadigzadig
    mysql.persistence.enabledWhether to enable persistent storagetruetrue
    mysql.persistence.sizeThe size of the persistent storage PVC20Gi20Gi

    If you use own MySQL

    Before installing the Zadig system, manually create the Database specified by connections.mysql.db.dex to ensure the normal installation of the Zadig system

    # Other Parameters

    KeyDescriptionExampleDefault
    kubernetes.serverKubernetes API Server addresshttps://10.0.0.1:6443nil
    gloo.k8s.clusterNameCluster namecluster.localcluster.local
    protocolAccess protocolhttpshttp

    ← Local SetupOfficial Script→

    资源
    教程
    论坛
    博客
    公司
    关于
    客户故事
    加入我们
    联系我们
    微信扫一扫
    hello@koderover.com

    © 2026 筑栈(上海)信息技术有限公司 沪 ICP 备 19000177 号 - 1

    •  跟随系统
    •  浅色模式
    •  深色模式
    •  阅读模式